Update e2e_test expectation to look for more consistent message. #2630
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These e2e tests have been extremely flaky requiring many retries (these tests are configured to have 3 retries each) and still sometimes failing.
See failing job here:
https://github.com/dart-lang/webdev/actions/runs/15444512522/job/43470375587
Failures all occur due to the missing "Succeeded" message from the build runner logs. Sometimes the build runner process ends without printing this success message:
https://github.com/dart-lang/build/blob/master/build_runner_core/lib/src/generate/build.dart#L216
The updated messages all appear directly before the "Succeeded" message would and indicate the last expected action was successful.
Associated issue: #2489